Document cross-machine plugin bundle download behavior - #3807
Document cross-machine plugin bundle download behavior#3807mintlify[bot] wants to merge 2 commits into
Conversation
Generated-By: mintlify-agent Mintlify-Source: dashboard-editor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
dosubot
Bot
added
size:XS
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Internal previewPreview URL: https://mcp-inspector-pr-3807.up.railway.app |
|
Closing: this docs PR conflicts with main; the Mintlify bot regenerates an up-to-date PR when the docs change again. |
Pull request was closed
1 participant
Added a new "Running plugins on a different machine" section to
docs/inspector/plugins.mdxexplaining that MCPJam now automatically attempts to download a plugin's stored bundle from the cloud when opened on a machine where it hasn't been imported before, only falling back to the manual re-import prompt if the download fails.Files changed:
docs/inspector/plugins.mdx— added "Running plugins on a different machine" section before "Credential setup"Summary by cubic
Documented how MCPJam runs plugins on different machines: for plugins with a local stdio component, it auto-downloads the stored bundle from the cloud and runs it if the content matches the pinned hash; it only prompts to re-import if the download fails. Added a new "Running plugins on a different machine" section to
docs/inspector/plugins.mdx.Written for commit 529f8c2. Summary will update on new commits.